Methods and systems for controlling access to relationship information in a social network

ABSTRACT

Systems and methods for controlling access to relationship information in a social network are described. One described method comprises receiving a request from an observer for relationship information indicating at least a first relationship between a target in a social network and a second entity in the social network, identifying at least a first privacy rule for the first relationship, and outputting at least part of the relationship information to the observer if the first privacy rule is satisfied.

FIELD OF THE INVENTION

The invention generally relates to social networks. More particularly, the invention relates to systems and methods for controlling access to relationship information in a social network.

BACKGROUND

Conventional social networks provide their members with the ability to form relationships with other members of the social network. Once members form relationships with each other, they often can view more of each other's profile information, including such information as a name, pictures, interests, etc. Additionally, members of the social network can typically view an interface showing the members with which a particular member has relationships. Some social networks allow members to share expanded profile information with their network friends and friends of those friends. Such social networks do not, however, effectively control access to relationship information, such as information indicating the existence and type of relationships between social network members.

SUMMARY

One embodiment of the present invention provides a method for controlling access to relationship information in a social network. For example, one such method includes receiving a request from an observer for relationship information indicating a relationship between one member of a social network and another entity in the social network, identifying a privacy rule for the relationship between the member and the entity, and outputting at least part of the relationship information to the observer if the privacy rule is satisfied. The privacy rule may be identified, for example, by accessing a privacy rule received from the member of the social network prior to the request.

This illustrative embodiment is mentioned not to limit or define the invention, but to provide one example of an embodiment of the invention to aid understanding thereof. Illustrative embodiments are discussed in the Detailed Description, and further description of the invention is provided there. Advantages offered by the various embodiments of the present invention may be further understood by examining this specification.

BRIEF DESCRIPTION OF THE DRAWINGS

These and other features, aspects, and advantages of the present invention are better understood when the following Detailed Description is read with reference to the accompanying drawings, wherein:

FIG. 1 illustrates a method in accordance with one embodiment of the present invention and an illustrative environment for carrying out the method;

FIG. 2 illustrates a diagram of an illustrative social network in accordance with one embodiment of the present invention;

FIG. 3 illustrates an illustrative user interface in accordance with one embodiment of the present invention;

FIG. 4 illustrates an illustrative social network structure for the social network illustrated in FIG. 2;

FIG. 5 illustrates another illustrative user interface in accordance with one embodiment of the present invention; and

FIG. 6 illustrates a diagram of an illustrative system in accordance with one embodiment of the present invention.

DETAILED DESCRIPTION Introduction

Embodiments of the present invention comprise methods and systems for controlling access to relationship information in a social network. There are multiple embodiments of the present invention. By way of introduction and example, one illustrative embodiment of the present invention provides a method for allowing a member of a social network to control which of the member's relationships are visible to other members of the social network. For example, within a social network, a member may have a group of co-workers and a group of dating friends. The member may not want the member's co-workers to be able to discover who the member is dating by accessing the social network. Certain embodiments of the present invention allow the member to limit the members of the social network who can view with whom the member has relationships and to limit the information about the relationship that is available (e.g., the type of relationship). The control of relationship information may be accomplished, for example, by allowing the member who wishes to limit such information to designate privacy rules for the member's relationships. Such control may also be accomplished, for example, by allowing social network members to establish groups of relationships and indicate privacy rules for the groups. The privacy rules may indicate criteria for accessing profile or relationship information within the social network. For example, a member of the social network can create a privacy rule or rules indicating that dating friends can see a display indicating the member's co-workers, but that co-workers cannot see a display indicating the dating friends of the member. Thus, certain embodiments of the present invention facilitate the protection of the member's privacy, not only for profile information, but for relationship information as well.

This introduction is given to introduce the reader to the general subject matter of the application. By no means is the invention limited to such subject matter. Illustrative embodiments are described below.

Processes

FIG. 1 shows an illustrative method 100 for controlling access to relationship information within a social network. A social network can refer to a computer network connecting entities, such as people or organizations, by a set of social relationships, such as friendship, co-working, or information exchange. Of course, a social network can also refer to a computer application or data connecting such entities by such social relationships. Social networks are discussed further below.

The first section below, entitled “Brief Overview of an Illustrative Method,” provides a brief overview of the illustrative method 100 with reference to FIG. 1. Then, in the sections following the first section, the various blocks in FIG. 1 will be described in more detail with references to FIGS. 1 through 5. Finally, illustrative system architectures that may be used in carrying out methods according to the present invention are described with reference to FIG. 6.

Brief Overview of an Illustrative Method

FIG. 1 shows an illustrative environment 180, 188 that may be used to perform that which is shown in each block shown in the method 100. FIG. 1 depicts a social network engine 180 that includes a relationship processor 182, a privacy module 184, and a display processor 186 that has access to a social network database 188. These system components making up the social network engine 180 comprise computer processors having access to code for carrying out the methods described. The system components shown in FIG. 1 are mentioned only briefly here, and are described in further detail below with reference to FIG. 6. To aid in understanding, the system component in the illustrative social network engine 180 shown in FIG. 1 is shown above the blocks in the method 100 that the component is responsible for facilitating.

According to the illustrative method 100, the relationship processor 182 receives a request from a member of a social network seeking relationship information of another member of the social network (block 102). For convenience, the member requesting the relationship information will be referred to as the “observer” or “requesting member,” and the profile of the member for whom relationship information is requested will be referred to as the “target” profile (and the member as the “target” member). For example, the observer may transmit a request seeking a display showing members of the social network that the target member classifies as “friends.” After receiving the request, the relationship processor 182 identifies all relevant relationships between the target and other entities in the social network, including relationships with the observer, if any (block 103). These relevant relationships may be identified, for example, by accessing a database containing a list or table of relationships and their types for the target member. The entities in the social network may include, for example, other members, other profiles, or communities within the social network.

After identifying the relevant relationships of the target profile, the privacy rule module 184 identifies a privacy rule for each of the relationships (block 104). The privacy rule for a relationship defines those that have permission to access information about the relationship. The privacy rule for a relationship may also indicate conditions for displaying profile information. Such privacy rules may have been previously specified, for example, by the target member. The privacy rule may be, for example, that “best friends” can know of the relationship and its type, “friends” can know of the relationship but not its type, and others cannot know of either the relationship or its type. Additionally, a privacy rule may allow a member to keep information regarding which communities the member is a part of confidential.

Once the privacy rules for the relevant relationships are identified, the privacy rule module 184 determines whether the requesting member of the social network satisfies the privacy rules 106. For the privacy rules that are satisfied, a display processor 186 outputs appropriate relationship information and user data as determined by the privacy rule 108. To output profile information, the display processor 186 may retrieve user data referenced by the privacy rule from a social network database 188. If the privacy rule is not satisfied for a relationship, the observer (i.e., the requester) is denied access to the requested relationship information.

With this overview in place, the illustrative method 100 will now be described in further detail. FIGS. 1 through 6 are referenced throughout the following description to help explain the various components of the illustrative method 100. The section below entitled “Receiving a Request for Relationship Information” amplifies on block 102 of FIG. 1. The next section, entitled “Illustrative Social Networks,” discusses illustrative social network environments. The following sections, “Identifying Relationships” and “Identifying Privacy Rules,” amplify on blocks 103 and 104 of FIG. 1, respectively. The section entitled “Identifying Privacy Rules” includes a section entitled “Illustrative Privacy Rules” that provides examples of various privacy rules. Next, a section entitled “Identifying Whether the Privacy Rule is Satisfied” amplifies on block 106 of FIG. 1. Then, sections entitled “Outputting Relationship Information,” “Privacy Rules for Profile Information,” and “Denying Access to Relationship and Profile Information” amplify on blocks 108 and 110 of FIG. 1. Finally, illustrative system environments that may be used in association with the present invention are discussed.

Receiving a Request for Relationship Information

The illustrative method 100 shown in FIG. 1 begins in block 102 where the relationship processor 182 receives a request for relationship information. The relationship information may include data indicating an existence of a relationship between any two entities in the social network such as a relationship between two members, between a member and a community, or between two communities. In addition to indicating the existence of a relationship, the relationship information may further indicate a type of a relationship, a weight of a relationship, a level of a relationship, when a relationship was formed, or another suitable aspect of a relationship.

There are various ways a request for relationship information can be received. In one embodiment, the social network engine 180 receives a request for relationship information when the observer is logged into a social network and clicks on an icon representing the target member of the social network. For example, an observer O within a social network 200, as illustrated in FIG. 2, may desire to view relationship information associated with a target T. The target T has relationships with members M₁, M₂, and M₃. The observer O may request relationship information for the target T by using a user interface, such as the user interface 300 illustrated in FIG. 3. According to one embodiment, the relationship information can be requested by an agent of observer O that has permission to access information on behalf of the observer O.

The user interface 300 illustrated in FIG. 3 is a web page and includes a member icon 302 along with profile data 320 and a member network display 304. The member network display 304 can show icons for each entity that has a relationship with the member whose icon 302 and profile data 320 are being displayed. For example, for the social network 200, if the member icon 302 represents the observer O, then the member network display 304 can include icons 306 and 308 representing profiles for target T and member M₄. The observer may request relationship information about the target T by selecting the icon 306, for example. The relationship processor 182 receives this request and proceeds to identify all relationships for the target T as illustrated in block 103.

Illustrative Social Network

To better explain how the relationship processor 182 identifies the relationships for a target profile, it is helpful to discuss the social network 200 illustrated in FIG. 2 in more detail. As mentioned above, the illustrative social network 200 illustrated in FIG. 2 comprises user profiles M₁-M₅, target profile T and observer profile O represented by vertices in a data graph. The types of relationships illustrated in FIG. 2 include co-worker relationships, friendship relationships, and dating relationships and are represented by differing types of edges between the vertices representing the profiles M₁-M₅, target T and observer O. For example, a friendship relationship from observer O to target T is represented by a solid edge extending from the vertex representing the observer O to the target T; and a co-worker relationship between the observer O and the target T is represented by a dotted edge from the vertex representing observer O to the vertex representing target T.

The co-worker, friendship, and dating relationships may be either directed relationships or undirected (also known as bi-directional) relationships. Directed relationships indicate which profile originated a relationship and allow for non-symmetrical relationships between profiles. For example, directed relationship can permit a first member to indicate that a second member of the social network is a best friend, and the second member to indicate only an acquaintance relationship with the first member. Directed relationship can be represented in a data graph with one way directed edges between profiles. For example, in the social network 200, there is a directed relationship from member M₅ to the member M₄ which the member M₄ has not reciprocated. Thus, there is not a relationship extending from member M₄ back to member M₅. The member M₄ may not have reciprocated the relationship because the member M₄ has not logged on to the social network since the member M₅ established the relationship, or because member M₄ does not desire to indicate a relationship with the member M₅. Directed relationships can offer more control to members of a social network for creating and accepting relationships with another member because each party to the relationship can agree that the relationship exists.

Undirected (or bi-directional) relationships can indicate a relationship between members of the social network without distinguishing a direction for the relationship or an indication of who created the relationship. Such relationships may not require reciprocation in order to be formed. For example, if a first member indicates a relationship with a second member of the social network in a model using only undirected relationships, a relationship as indicated by the first member may be created between the first member and the second member without the need for the second member to reciprocate or indicate a relationship with the first member.

The relationships illustrated in FIG. 2 may be of varying types, weights and levels. For example, the friendship relationship from the target T to member M₂ can be a “best friend” level of friendship relationship whereas the friendship relationship between member M₂ and M₄ may only be an “acquaintance” level of friendship relationship. Within a given level of relationship, a weight may also be indicated. A weight of relationship can distinguish between relationships of a similar type and level. For example, a user may weight one best friend relationship higher than another best friend relationship.

Additionally, within a social network, a degree of separation between two profiles can be determined by identifying the fewest number of edges separating the two profiles. The path found by the fewest number of edges separating two related profiles can be referred to as a shortest path. For example, in the social network 200, the shortest path from observer O to member M₄ may comprise the friendship relationship directly from the observer O to the member M₄ instead of the longer path by way of target T and member M₂, for example. According to one embodiment, a degree of separation may be determined by use of a weighting factor assigned to each relationship. For example, close friendships may be weighted higher than acquaintances. A degree of separation for weighted relationships may be inversely proportionate to the weight of the relationships, so that a path between more heavily weighted relationships would have a lower degree of separation than a path between less heavily weighted relationships.

Within a social network, members may use privacy rules to control access to relationship and profile information. The privacy rules may be based on any suitable attribute of a relationship including a weight of a relationship, level of a relationship, type of a relationship, or degree of separation. To facilitate such privacy rules the social network engine 180 may maintain relationship information in a form represented by the data graph illustrated in FIG. 4. The graph illustrated in FIG. 4 facilitates privacy rules based on different weights and types of relationships by indicating each type and weight of relationship with a “group” vertex that is associated with the profiles comprising the relationship. The group vertex appears in the data graph between one entity in the social network and other entities that are members of the group. For convenience, the group vertices will be symbolically represented g_(x)(N) where x designates the type of group and N designates the profile creating the group. For example, in FIG. 4, target T has three groups: g_(f)(T) representing the group of the target T's friends; group g_(c)(T) representing the group of the target T's co-workers; and group g_(d)(T) representing the group of the target T's dating relationships. While the vertices in FIG. 4 are described as representing member profiles, the methods described work equally well with other social network entities such as communities, events or agents. Communities within a social network can comprises groups of entities that facilitate sharing information such as common interests, activities, etc. Events within a social network can comprise, for example calendar events that can be associated with attendees and provide event information. Agents in a social network can comprise entities that have permission to access information on behalf of another social network entity.

The data graph structure illustrated in FIG. 4 allows all relationships to be represented with a single type of edge. Differing types of relationship edges are not required since the group vertices distinguish what type, level, and weight of relationship exists between related entities. For example, the data graph illustrated in FIG. 4 represents the same social network 200 illustrated in FIG. 2, but instead of requiring differing types of edges between profile vertices, such as the friendship edges, co-worker edges, etc., the data graph in FIG. 4 uses a singe type of edge and represents types and weights of relationships with group vertices. For example, Target T in FIG. 2 has three types of relationships with other profiles. A co-worker relationship with member M₁, a friendship relationship with member M₂ and observer O, and a dating relationship with member M₃ and the observer O. In the data graph structure illustrated in FIG. 4, these types of relationships are illustrated by the three groups g_(f)(T), g_(c)(T) and g_(d)(T), which are connected to each profile who is a member of each respective group. Thus the group g_(f)(T) is connected to member M₂ and observer O, group g_(c)(T) is connected to the member M_(I), and group g_(d)(T) is connected to member M₃ and the observer O.

The group vertices illustrated in FIG. 4 are connected by a first edge extending to the group vertex from the profile that created the group and by a second edge from the group vertex to another group vertex or to a social network entity that is a member of the group. For example, the co-worker relationship between target T and observer O includes a first edge to the group g_(c)(T) and a second edge from the group g_(c)(T) to observer O. According to the data graph structure illustrated in FIG. 4, social network entities are connected to other social network entities through at least one group vertex.

Groups may also be connected to other groups. Connections between groups indicate whether members of one group have permission to access information from members of another group. According to one embodiment, the connections between groups and profiles, and between two groups are directed relationships. For example, target T's dating group g_(d)(T) has a one-way relationship connecting it to the co-worker group g_(c)(T) representing that members of target T's dating group can view members of target T's co-worker group. The absence of a connection from the co-worker group g_(c)(T) to the dating group g_(d)(T) represents, that members of target T's co-worker group cannot view members of target T's dating group.

The illustrative social network 200 as depicted in FIG. 4 will be used below to further discuss blocks 103-106 of the illustrative method 100. While each of the entities illustrated in FIG. 4 represents a member profile, it should be understood that the methods discussed in connection with FIG. 4 work equally well with other social network entities such as communities, etc.

Identifying Relationships

Returning now to block 103, the relationship processor 182 identifies all relationships for the target T. According to one embodiment, a specified degree of separation can be used to limit the number of relationships that will be identified. For example, it can be determined that only relationships up to two degrees of separation are of interest, and in block 103 relationships that are two degrees or less from the target T will be identified. For purposes of example, all first degree relationships for the target T in the social network 200 as show in FIG. 4 are listed below:

1. T→g_(f)(T)→O

2. T→g_(f)(T)→M₂

3. T→g_(c)(T)→M₁

4. T→g_(d)(T)→O

5. T→g_(d)(T)→M₃

6. T→g_(d)(T)→g_(c)(T)→M₁

As seen above, in this illustrative embodiment, all relationships between social network entities will pass through a group vertex. Group vertices can also be connected to other group vertices. For example in relationship 6 above, the target T has a relationship with member M₁ by virtue of the target T's dating group g_(d)(T) having an edge to the target T's co-worker group g_(c)(T). According to one embodiment, relationships may be identified in a breadth first search starting with the target profile continuing for the specified degree of separation or until a branch of the search leads back to the target profile.

Identifying Privacy Rules

Once the relationships for the target T are identified, the social network engine 180 identifies a privacy rule for the relationship as illustrated in block 104 of FIG. 1. A privacy rule for a relationship may comprise any suitable access criteria that designate conditions for when relationship information may be accessed by other members of the social network. For each relationship, the group vertices forming the relationship can identify the privacy rules for that relationship. For example, in relationship 1 above between the target T and observer O, the group vertex containing the privacy rule for this relationship is the group g_(f)(T). Privacy rules can indicate a minimum weight of relationship, a degree of separation, a type of relationship, or other suitable criterion designating which members of the social network may view the relationship information. For example, a privacy rule can be set up that would allow a member's co-worker to see other co-workers but not allow the co-worker to see the member's dating relationships. Some specific examples of privacy rules are discussed below.

Illustrative Privacy Rules

Illustrative types of privacy rules include 1) Private to user, 2) Neighbors in a group, 3) Two neighbors of a group, 4) Across two different groups, 5) Across two different groups' two neighbors, and 6) Public. It should be understood that this is only a list of possible types of privacy rules and merely provides illustrative privacy rules that may be used by embodiments of the present invention. By no means are these the only types of privacy rules that may be used. According to other embodiments, any suitable designation of a degree of separation, relationship weight, relationship type, profile characteristic, or other suitable social network attribute may be used to designate a privacy rule.

A “private to a user” privacy rule can indicate that the only member of the social network who can view or access the relationship information is the profile that created the relationship. For example, a member of the social network may want to keep relationship information about who the member is dating completely confidential. In such a situation, the member may use a “private to a user” privacy rule to ensure the dating relationships are not visible to other members of the social network.

A “neighbors of a group” privacy rule can indicate that members within a certain group, for example a “friends” group, can see other members of the same group, but that the members of that group are not visible to members outside of the group. For example, in the social network 200, target T's friend member M₂ can be permitted to view friend observer O but not dating friend M₃.

A “two neighbors of a group” privacy rule can allow members of a group to act as intermediaries for relationships. For example, profiles with a relationship with a member of a group can be permitted to view other members of that group. For example, in the social network 200, member M₄ is not directly a friend of target T, but is a friend of member M₂, who is a friend of target T. Therefore, according to a “two neighbors of a group” privacy rule, member M₄ could be permitted to view target T's relationship with observer O based on the relationship with intermediary member M₂.

An “across two different groups” privacy rule can allow members of one group to see relationships for members of another group in a one-way fashion. For example, members of a best friends group can be permitted see members of an acquaintances group, but members of the acquaintances group can be restricted from seeing the best friends group.

An “across two different groups' two neighbors” privacy rule can function similar to the “two neighbors of a group rule” by allowing members of one group to see relationships for members of another group in a one-way manner, but can further allow friends of one group to see relationships for another group. For example, members of a best friends group and other members with relationships to the members of the best friends group can be permitted to see members of an acquaintances group, but not visa versa.

A “public” privacy rule can permit all members of the social network to see the corresponding relationship or profile information.

Identifying Whether the Privacy Rule is Satisfied

After identifying a privacy rule for a relationship, the privacy rule module 184 determines whether the privacy rule is satisfied as illustrated in block 106 of FIG. 1. Since, in one embodiment, privacy rules are controlled by the profile that created the corresponding relationship, this may involve checking a privacy rule for a relationship from the target T to a related member of the social network and checking a privacy rule for a relationship from the related member back to the target T. For example, in FIG. 4, to determine whether the observer O has permission to view the target T's relationship with members M₂ and M₃, one or more relationships from the target T to the observer O are identified. In the social network 200, this can be the relationship M₂→g_(d)(T)→O, for example.

Once one or more relationships from the target profile T to the observer O are identified, the group or groups forming the relationship are identified. Identifying the group or groups that make up the relationship from a target profile to an observer profile allows the privacy rule module 184 to identify the groups which will control access to the relationship. For example, for the relationship T→g_(d)(T)→O in the social network 200, the group forming the relationship or in other words the group through which the relationship passes—is the target T's dating group g_(d)(T). Thus, the privacy rule module 224 will use the privacy rules for this group in determining whether access to relationships with the target T by the observer O including target T's dating group g_(d)(T) are permitted.

Because the profile originating a relationship may control access to that relationship, any relationship information available to the observer O about the target profile T must at least “pass through” this group. In other words, any relationship with the target profile T visible to the observer O must include target T's dating group g_(d)(T). For example, of the first degree relationships listed above for the target T, those “passing through” the group g_(d)(T) include relationships 4-6 listed below:

4. T→g_(d)(T)→O

5. T→g_(d)(T)→M₃

6. T→g_(d)(T)→g_(c)(T)→M₁

Note that if the relationship g_(d)(T)→g_(c)(T) between the dating relationship of the target T and co-workers of the target T did not exist, the relationship T→g_(d)(T)→g_(c)(T)→M₁ between the target T and member M₁ would not pass through target T's dating group g_(d)(T).

For the relationships that “pass through” the group g_(d)(T), the privacy rule associated with the group g_(d)(T) will determine in part whether these relationships are available to the observer O. For example, in order for the observer O to be able to access the relationship between the target profile T and profile M₁, the privacy rule for group g_(d)(T) set by the T must allow the access. This can occur, for example, if T has indicated a “neighbors in a group” privacy rule that allows members of group g_(d)(T) to view other members of group g_(c)(T). For example, the target T may want dating friends to be able to view co-workers, but may not want co-workers to be to view the target T's dating friends.

Because the profiles that have relationships with the target T may also control access to their own relationships with the target T, the privacy rules for the groups connecting the members back to the target must also allow access by the observer O. For example, consider the relationship M₁→g_(c)(M₁)→T between the profile M₁ and the target T. This relationship passes through the co-worker group g_(c)(M₁) for the member M₁, so the co-worker group g_(c)(M₁) must have a privacy rule allowing access to the observer O. For the relationship illustrated in FIG. 2, this means that the privacy rule for the profile M₂ would have to indicate a broad permission, such as a public level privacy rule. A broad permission privacy rule would be required in this example because the profile M₁ is not directly connected to the observer O, and does not have a relationship that allows it to view the observer's profile—note that there is no connection from the co-worker group g_(c)(T) of the target T to the dating group g_(d)(T) of the target T, but only a one-way connection from g_(d)(T) to g_(c)(T). The practical significance of this can be seen in that the member M₁ has only indicated a co-worker relationship with the target T and cannot see target T's dating friends. Member M1 should be able to control who can know he is a co-worker of the target T and so can indicate a privacy rule for the group g_(c)(M₁).

That such a rule may be required can thus be consistent with protecting relationship information since relationship information should generally not be available to entities that the profile creating the relationship is unaware of, unless that profile has indicated a broad permission level such as a public level privacy rule for the group making up the relationship. For example, the member M₁ may not consider the group of co-workers g_(c)(M₁) private and can thus have indicated a broad permission, by way of a public level privacy rule for example, for the co-worker group allowing it to be accessed by the entire social network.

According to one embodiment, determining whether a privacy rule is satisfied may comprise identifying a union of privacy rules. For example, target T has a relationship with observer O by both a dating relationship and a friendship relationship. When determining a privacy rule for information that observer O is permitted to see regarding relationships with target T, the privacy rule module 184 can identify a union of the privacy rules for dating relationships and for friendship relationships. For example, target T can indicate that dating friends can view coworkers but not friendship relationships, and that friends can view other friends but not coworkers. If the observer O then requests relationship information for target T, the observer O will be permitted to see both the dating relationship with member M₃ and the coworker relationship with member M₁ because of the union of dating privacy rules and friendship privacy rules.

Outputting Relationship Information

Referring again to FIG. 1, if the social network engine 180 determines that a privacy rule is satisfied, the method 100 proceeds to block 106, wherein the display processor 186 outputs the relationship information if the access criterion is satisfied 110. Outputting the relationship information if the access criterion is satisfied may comprise selectively outputting relationship information, indicating a secrecy status for relationship information, outputting a warning for negative relationships, or other suitable ways of regulating relationship information based on the access criterion.

According to one embodiment, an illustrative user interface 500 as shown in FIG. 5 may be used to output the relationship information. The illustrative user interface 500 shows a web page similar to the user interface 300 illustrated in FIG. 3. The illustrative user interface 500 shown in FIG. 5 displays a member icon 502, profile data 520, and a member network display 504. The member network display 504 in FIG. 5 presents icons representing member M₁ and M₂ that comprise two of the profiles related to the target T. The member M₃ is also related to the target T, but is not shown in FIG. 5 to demonstrate that the member M₃ may have indicated a privacy rule preventing observer O from seeing the relationship M₃→g_(d)(M₃)→T. For example, the member M₃ can indicate that this relationship is private to the member M₃. Thus even though a privacy rule for the relationship T→g_(d)(T)→M₃ may allow the observer O to view information for the member M₃, the privacy rule for the member M₃ may still prevent profile or relationship information from being presented to the observer O.

Depending on the privacy rule, relationship information or profile data may be selectively output. Selectively outputting information can comprise, for example, outputting information regarding the existence, type, and weight of a relationship and preventing access to remaining relationship information based on whether the access criterion is satisfied. For example, the social network engine 180 can output information indicating an existence of a relationship between observer O and the target T, but, depending on the privacy rule for the relationship, may not output information about the type or weight of the relationship. Thus, for example, an output similar to the network display 504 may be presented showing icons indicating which profiles have relationships with the profile represented by the icon 502, but may not contain information indicating the type of the relationship. According to one embodiment, sub-classification information—such as a level of friendship—can be kept private so that a display showing a network of a social network member will not reveal the sub-classification of related social network entities. For example, a network display can present to an observer all friends of a member including acquaintances, close friends, and best friends of the member, but not reveal to the observer the sub-classifications of the member's friends.

Indicating a secrecy status for relationship information may comprise, for example, outputting a designation in connection with relationship information informing a member of the social network viewing the relationship information that the relationship information is confidential or should be kept a secret. For example, target T may allow observer O to see that the dating relationship with member M₃ but may not want the information shared with other members of the social network. According to one embodiment, the relationship information can thus be displayed along with an indication of its confidential status. This can enable observer O to realize that the dating relationship between the target T and member M₃ is to be kept secret.

Outputting a warning for negative relationships may comprise determining whether a relationship with a first profile will also form a relationship between a member and a second profile with which the member profile has indicated a negative relationship. For example, target T can indicate a negative relationship indicating, for example, that member M₄ is an enemy. Member M₂ can have a relationship with the member M₄ by a friendship relationship as illustrated in the illustrative social network 200. Member M₂ can further invite target T to form a friendship relationship T→g_(f)(T)→M₂ with the member M₂. Because the proposed relationship with the member M₂ will create a second degree relationship between target T and member M₄ (a friend-of-a-friend relationship), the display processor 186 can output a warning to target T indicating that the relationship with member M₂ may also create a relationship with member M₄ with whom the target T has indicated a negative relationship.

Privacy Rules for Profile Information

In addition to controlling access to relationship information based on privacy rules for a relationship, the social network engine 180 may also control access to profile information based on privacy rules. Controlling access to profile information may comprise, for example, selectively outputting profile information, outputting a secrecy status for profile information, and other suitable methods of controlling access to profile information, such as the methods discussed above for controlling access to relationship information. For example, the social network engine 180 can allow a member to indicate that certain profile information, such as a telephone number for example, should only be shared with best friends. The social network engine 180 can then selectively output the member's telephone number to members that have relationships with profiles related to target T by a best friend level of relationship.

According to one embodiment, privacy rules for profile information may be associated with groups as discussed above in connection with relationship information. For example, when determining what profile information to display for the target T, the privacy rule module 184 can identify privacy rules for the groups g_(d)(T) and g_(f)(T) that connect profile T to the observer O. In addition to indicating conditions for sharing relationship information, the privacy rule associated with the groups g_(d)(T) and g_(f)(T) can also designate which profile information is to be displayed to members of the group. For example, the target T may indicate a work phone number for the friendship group g_(f)(T) and a home phone number for the dating friends group g_(d)(T).

Privacy rules for profile information can “flow through” groups in a manner similar to the methods discussed above in connection with relationship information. For example, the relationship processor can identify which profile information to present to the observer O for the profile M₃ by first identifying the relationship M₃→g_(d)(M₃)→T→g_(d)(T)→O and the relationship M₃→g_(d)(M₃)→T→g_(f)(T)→O and then identifying the privacy rule for the groups that are part of the relationship. Thus, in this example, the privacy rule for the group g_(d)(M₃) and for the groups g_(d)(T) and g_(f)(T) would determine which profile information the observer O can see about profile M₃. So, for example, the target T may grant permission to access information about the relationship T→g_(d)(T)→M₃, but the member M₃ may only indicate a private to a user privacy rule for the group g_(d)(M₃), in which case profile information for the member M₃ would not be available to the observer O.

Denying Access to Relationship and Profile Information

Referring to blocks 106 and 110 of FIG. 1, if the privacy rule module 184 determines that the privacy rules controlling the relationship for which the observer O has requested information is not satisfied, then the display processor 186 can deny the observer O access to the requested information 110. Denying access to the observer O may comprise, for example, outputting a message that the requested information is not available, not updating a display of the social network in response to the request, or only outputting allowed information and withholding other relationship or profile information. For example, an observer may click on a link representing a target e in a social network. In response to the request, the relationship processor 182 identifies all relationships of the target T as discussed above. After identifying these relationships, a privacy rule for each one may be identified and the privacy rule module 184 can determine whether the privacy rules are met. If none of the rules are met, the display processor 186 can output an indication to the observer O that no information about the requested target is available.

System Architecture

Various systems in accordance with the present invention may be constructed. FIG. 6 shows an illustrative system in which illustrative embodiments of the present invention, such as those discussed in connection with FIGS. 1-5, may operate. The present invention may operate, and be embodied in, other systems as well.

The system 600 shown in FIG. 6 comprises multiple client devices 602 a-n in communication with a server device 604 over a network 606. In one embodiment, the network 606 comprises the Internet. In other embodiments, other networks, such as an intranet, WAN, or LAN may be used. According to another embodiment, the network 606 may comprise servers attached to the network 606. Moreover, methods according to the present invention may operate within a single computer.

The client devices 602 a-n shown in FIG. 6 each comprises a computer-readable medium, such as a random access memory (RAM) 608 coupled to a processor 610. The processor 610 executes computer-executable program instructions stored in memory 608. Such processors may comprise a microprocessor, an ASIC, and state machines. Such processors comprise, or may be in communication with, media, for example computer-readable media, which stores instructions that, when executed by the processor, cause the processor to perform the steps described herein. Embodiments of computer-readable media include, but are not limited to, an electronic, optical, magnetic, or other storage or transmission device capable of providing a processor, such as the processor 610 of client 602 a, with computer-readable instructions. Other examples of suitable media include, but are not limited to, a floppy disk, CD-ROM, DVD, magnetic disk, memory chip, ROM, RAM, an ASIC, a configured processor, all optical media, all magnetic tape or other magnetic media, or any other medium from which a computer processor can read instructions. Also, various other forms of computer-readable media may transmit or carry instructions to a computer, including a router, private or public network, or other transmission device or channel, both wired and wireless. The instructions may comprise code from any suitable computer-programming language, including, for example, C, C++, C#, Visual Basic, Java, Python, Perl, and JavaScript.

Client devices 602 a-n may also comprise a number of external or internal devices such as a mouse, a CD-ROM, DVD, a keyboard, a display, or other input or output devices. Examples of client devices 602 a-n are personal computers, digital assistants, personal digital assistants, cellular phones, mobile phones, smart phones, pagers, digital tablets, laptop computers, Internet appliances, and other processor-based devices. In general, a client device 602 a may be any type of processor-based platform that is connected to a network 606 and that interacts with one or more application programs. Client devices 602 a-n may operate on any operating system capable of supporting a browser or browser-enabled application, such as Microsoft® Windows® or Linux. The client devices 602 a-n may include, for example, personal computers executing a browser application program such as Microsoft Corporation's Internet Explorer™, Netscape Communication Corporation's Netscape Navigator™, and Apple Computer, Inc.'s Safari™.

Through the client devices 602 a-n, users 612 a-n can communicate over the network 606 with each other and with other systems and devices coupled to the network 606. As shown in FIG. 6, a server device 604 is also coupled to the network 606.

The server device 604 shown comprises a server executing a social network engine application program, also known as a social network engine 180. The social network engine 180 allows users, such as user 612 a, to interact with and participate in a social network. As mentioned above, a social network can refer to a computer network connecting entities, such as people or organizations, by a set of social relationships, such as friendship, co-working, or information exchange. Of course, a social network can refer to a computer application or data connecting such entities by such social relationships. Examples of social networks include Orkut.com and Friendster.com.

Social networks can comprise any of a variety of suitable arrangements. An entity or member of a social network can have a profile and that profile can represent the member in the social network. The social network can facilitate interaction between member profiles and allow relationships between member profiles. As discussed above, relationships between member profiles may be reciprocal relationships. For example, a first member can invite another member to form a relationship with the first member and the other member can accept or reject the invitation. A member may also categorize or weigh the relationship with other member profiles, such as, for example, by assigning a level to the relationship. For example, for a friendship-type relationship, the member can assign a level, such as acquaintance, friend, good friend, and best friend, to the relationships between the member's profile and other member profiles. In one embodiment, the social network engine 180 can determine the type of relationship between member profiles, including, in some embodiments, the degree of separation of the relationship and the corresponding weight or level of the relationship.

Similar to the client devices 602 a-n, the server device 604 shown comprises a processor 616 coupled to a computer-readable memory 618. Server device 604, depicted as a single computer system, may be implemented as a network of computer processors. Examples of a server device 604 are servers, mainframe computers, networked computers, a processor-based device, and similar types of systems and devices. Client processor 610 and the server processor 616 may be any of a number of computer processors, such as processors from Intel Corporation of Santa Clara, Calif. and Motorola Corporation of Schaumburg, Ill.

Server device 604 further comprises a social network engine 180 within memory 618. The social network engine comprises a relationship processor 182, a privacy rule module 184, and a display processor 186. As discussed above, the relationship processor 182 can identify relationships between entities within a social network. The relationship processor 182 can pass a set of identified relationships to the privacy rule module 184. The privacy module 184 can identify one or more privacy rules for each relationship and can further determine whether an observer within the social network satisfies the criteria specified by the privacy rule for accessing information about the corresponding relationship. A display processor 186 can then cause the output of the relationship information as indicated by the privacy rule.

Server device 604 also provides access to storage elements, such as a social network storage element, in the example shown in FIG. 6, a user data datastore 188. The datastore 188 may be used to store profile information, or other social network components. Data storage elements may facilitate any one or combination of methods for storing data, including without limitation, arrays, hash tables, lists, and pairs. Other similar types of data storage devices can be accessed by the server device 604. According to one embodiment, privacy rules can reference profile information to allow the display processor 186 to obtain the appropriate profile information to output to an observer within a social network. The social network engine 180 can receive data comprising the profiles and communities from the social network database 188 and can also send data comprising communities and profiles to the social network database 188 for storage. The social network database 188 may be physically attached or otherwise in communication with the social network engine 180 by way of a network or other connection.

It should be noted that the present invention may comprise systems having different architecture than that which is shown in FIG. 6. For example, in some systems according to the present invention, server device 604 may comprise a single physical or logical server. The system 600 shown in FIG. 6 is merely illustrative, and is used to help explain the illustrative method shown in FIG. 1.

General

While the above description contains many specifics, these specifics should not be construed as limitations on the scope of the invention, but merely as exemplifications of the disclosed embodiments. Those skilled in the art will envision any other possible variations that are within the scope of the invention. 

1. A computer-implemented method of processing a request to view relationship information, the method executed by at least one computing device comprising a processor, the method comprising: receiving a request via a communications network from a first user to view relationship information associated with a second user; identifying a first group vertex associated with the first user based on a database of social network information, wherein the social network information comprises relationship information and profile information received from users of the social network, the first group vertex representing a first type of user-established relationship and connecting via a one or more edges a first set of users having the first type of user-established relationship with the first user; identifying a second group vertex associated with the second user based on the database of social network information, the second group vertex representing a second type of user-established relationship and connecting via one or more edges a second set of users having the second type of user-established relationship with the second user; identifying a privacy rule associated with the first group vertex and the second group vertex based on the database of social network information; the processor determining whether the first user has rights to view the relationship information based on the privacy rule; and providing at least part of the relationship information to the first user via the communications network responsive to determining whether the first user has rights to view the relationship information.
 2. The method of claim 1, wherein identifying a privacy rule associated with the first group vertex and the second group vertex comprises: identifying one or more group vertices that connect the first group vertex with the second group vertex based on the database of social network information; and identifying a privacy rule associated with at least one of the one or more group vertices based on the database of social network information.
 3. The method of claim 1, wherein the privacy rule specifies that the first user has rights to view the relationship information based in part on a weight of the first type of user-established relationship.
 4. The method of claim 1, wherein the privacy rule specifies that the first user has rights to view the relationship information if the first type of relationship and the second type of relationship are the same type of user-established relationship.
 5. The method of claim 1, wherein the privacy rule specifies that the first user has rights to view the relationship information if the first group vertex and the second group vertex are connected by one vertex.
 6. The method of claim 1, further comprising: providing an indication that the first user is not permitted to access the relationship information responsive to determining that the first user does not have rights to view the relationship information.
 7. A computer system for processing a request to view relationship information comprising one or more computing devices, the system comprising: a database comprising social network information, wherein the social network information comprises relationship information and profile information received from users of the social network; a relationship processor stored in a memory associated with the one or more computing devices and executable to: receive a request from a first user to view relationship information associated with a second user via a communications network, identify a first group vertex associated with the first user based on the social network information, the first group vertex representing a first type of user-established relationship and connecting via one or more edges a first set of users having the first type of user-established relationship with the first user, and identify a second group vertex associated with the second user based on the social network information, the second group vertex representing a second type of user-established relationship and connecting via one or more edges a second set of users having the second type of user-established relationship with the second user; a privacy rule module stored in the memory associated with the one or more computing devices and executable by the processor to: identify a privacy rule associated with the first group vertex and the second group vertex based on the social network information, and determine whether the first user has rights to view the relationship information based on the privacy rule; and a display processor stored in the memory and executable to provide the relationship information to the user via the communications network responsive to determining whether the first user has rights to view the relationship information.
 8. The system of claim 7, wherein the relationship processor is further executable to: identify one or more group vertices that connect the first group vertex with the second group vertex based on the social network information; and identify a privacy rule associated with at least one of the one or more group vertices based on the social network information.
 9. The system of claim 7, wherein the privacy rule specifies that the first user has rights to view the relationship information based in part on a weight of the first type of user-established relationship.
 10. The system of claim 7, wherein the privacy rule specifies that the first user has rights to view the relationship information if the first type of user-established relationship and the second type of user-established relationship are the same type of user-established relationship.
 11. The system of claim 7, wherein the privacy rule specifies that the first user has rights to view the relationship information if the first group vertex and the second group vertex are connected by one vertex.
 12. The system of claim 7, wherein the display processor is further executable to provide an indication that the first user is not permitted to access the relationship information responsive to determining that the first user does not have rights to view the relationship information. 